<!DOCTYPE html>
<html>

<head>
  <meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta http-equiv="X-UA-Compatible" content="IE=edge">

<title>
  Hantsy
  
  Bai
  
  
  | Remote Deployment to Glassfish v6 using Cargo Local Deployer
  
</title>
<meta name="description" content="My personal website focusing on Java EE/Jakarta EE and Spring.
">

<!-- Open Graph -->


<!-- Bootstrap & MDB -->
<link href="https://stackpath.bootstrapcdn.com/bootstrap/4.5.2/css/bootstrap.min.css"
  rel="stylesheet" integrity="sha512-MoRNloxbStBcD8z3M/2BmnT+rg4IsMxPkXaGh2zD6LGNNFE80W3onsAhRcMAMrSoyWL9xD7Ert0men7vR8LUZg==" crossorigin="anonymous">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/mdbootstrap/4.19.1/css/mdb.min.css"
  integrity="sha512-RO38pBRxYH3SoOprtPTD86JFOclM51/XTIdEPh5j8sj4tp8jmQIx26twG52UaLi//hQldfrh7e51WzP9wuP32Q==" crossorigin="anonymous" />

<!-- Fonts & Icons -->
<link rel="stylesheet"
  href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.14.0/css/all.min.css"
  integrity="sha512-1PKOgIY59xJ8Co8+NE6FZ+LOAZKjy+KY8iq0G4B3CyeY6wYHN3yt9PW0XpSriVlkMXe40PTKnXrLnZ9+fkDaog==" crossorigin="anonymous">
<link rel="stylesheet"
  href="https://cdnjs.cloudflare.com/ajax/libs/academicons/1.9.0/css/academicons.min.css"
  integrity="sha512-W4yqoT1+8NLkinBLBZko+dFB2ZbHsYLDdr50VElllRcNt2Q4/GSs6u71UHKxB7S6JEMCp5Ve4xjh3eGQl/HRvg==" crossorigin="anonymous">
<link rel="stylesheet" type="text/css"
  href="https://fonts.googleapis.com/css?family=Roboto:300,400,500,700|Roboto+Slab:100,300,400,500,700|Material+Icons">

<!-- Code Syntax Highlighting -->
<link rel="stylesheet"
  href="https://gitcdn.link/repo/jwarby/jekyll-pygments-themes/master/github.css" />

<!-- Styles -->
<link rel="shortcut icon" href="/assets/img/favicon.ico">
<link rel="stylesheet" href="/assets/css/main.css">

<link rel="canonical" href="/blog/2020/remote-deployment-to-glassfish-v6-using-cargo-local-deployer/">

<!-- JQuery -->
<!-- jQuery -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js" integrity="sha512-bLT0Qm9VnAYZDflyKcBaQ2gg0hSYNQrJ8RilYldYQ1FxQYoCLtUjuuRuZo+fjqhx/qtq/1itJ0C2ejDxltZVFg==" crossorigin="anonymous"></script>


<!-- Theming-->

<script src="/assets/js/theme.js"></script>
<!-- Load DarkMode JS -->
<script src="/assets/js/dark_mode.js"></script>



<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-18SZ2W3GXD"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag() { dataLayer.push(arguments); }
  gtag('js', new Date());

  gtag('config', 'G-18SZ2W3GXD');
</script>




  
<!-- MathJax -->
<script type="text/javascript">
  window.MathJax = {
    tex: {
      tags: 'ams'
    }
  };
</script>
<script defer type="text/javascript" id="MathJax-script" src="https://cdn.jsdelivr.net/npm/mathjax@3.1.2/es5/tex-mml-chtml.js"></script>
<script defer src="https://polyfill.io/v3/polyfill.min.js?features=es6"></script>


  <link type="application/atom+xml" rel="alternate" href="/feed.xml" title="blank" />
  <!-- Begin Jekyll SEO tag v2.7.1 -->
<meta name="generator" content="Jekyll v3.9.0" />
<meta property="og:title" content="Remote Deployment to Glassfish v6 using Cargo Local Deployer" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="This is an addition to the existing deploying Jakarta EE 9 applications to Glassfish v6 using Cargo maven plugin. Cargo maven plugin 1.8.3 will include a glasfish6x containerId for the new Glassfish v6. In 1.8.2 or previous versions, it allows you use a JSR88 specification(Deployment) based remote deployer with a runtime configuration to deploy applications to a running Glassfish server. This will stop to work when switching to use a glassfish6x container due to the changes happen in Jakarta EE 9 and Glassfish v6. The JSR88 is removed in the further Jakarta EE 9, check the 6.1.4. Removed Jakarta Technologies section of Jakarta EE 9 specification. And the deployment-client artifact which is existed for Glassfish v5 release train is not available in Glassfish v6. Correspondingly cargo glassfish6x container will not include a remote deployer, and you can not configure a runtime configuration as before. But you can use the local deployer to deploy the applications to remote servers. &lt;profile&gt; &lt;id&gt;glassfish-local-deployer&lt;/id&gt; &lt;properties&gt; &lt;cargo.hostname&gt;localhost&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;8080&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;4848&lt;/cargo.glassfish.admin.port&gt; &lt;cargo.zipUrlInstaller.downloadDir&gt;${project.build.directory}/../installs &lt;/cargo.zipUrlInstaller.downloadDir&gt; &lt;/properties&gt; &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.codehaus.cargo&lt;/groupId&gt; &lt;artifactId&gt;cargo-maven2-plugin&lt;/artifactId&gt; &lt;configuration&gt; &lt;container&gt; &lt;containerId&gt;glassfish6x&lt;/containerId&gt; &lt;zipUrlInstaller&gt; &lt;url&gt; https://download.eclipse.org/ee4j/glassfish/glassfish-${glassfish.version}.zip &lt;/url&gt; &lt;downloadDir&gt;${cargo.zipUrlInstaller.downloadDir}&lt;/downloadDir&gt; &lt;/zipUrlInstaller&gt; &lt;!-- or use artifactInstaller--&gt; &lt;!--&lt;artifactInstaller&gt; &lt;groupId&gt;org.glassfish.main.distributions&lt;/groupId&gt; &lt;artifactId&gt;glassfish&lt;/artifactId&gt; &lt;version&gt;${glassfish.version}&lt;/version&gt; &lt;/artifactInstaller&gt;--&gt; &lt;/container&gt; &lt;configuration&gt; &lt;!-- the configuration use to deploy --&gt; &lt;home&gt;${project.build.directory}/glassfish6x-home&lt;/home&gt; &lt;properties&gt; &lt;cargo.hostname&gt;${cargo.hostname}&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;${cargo.servlet.port}&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;${cargo.glassfish.admin.port} &lt;/cargo.glassfish.admin.port&gt; &lt;cargo.remote.username&gt;admin&lt;/cargo.remote.username&gt; &lt;cargo.remote.password&gt;&lt;/cargo.remote.password&gt; &lt;/properties&gt; &lt;/configuration&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/build&gt;&lt;/profile&gt; The above configuration also work in the existing glassfish5x containerId. The side effect is you have to download a copy of Glassfish dist, the local deployer uses the Glassfish built-in asadmin tooling command to perform the deployment. NOTE: The cargo.hostname is the hostname/address of the target Glassfish server to deploy. Execute the following command to package and deploy the application to the target server. mvn clean package cargo:deploy -Pglassfish-local-deployer To undeploy the application, execute the following command. mvn cargo:undeploy -Pglassfish-local-deployer Check the Cargo official guide for the instructions of Remote Deployment to Glassfish v6 and the changes of Cargo glassfish6x containerid. &lt;hr&gt;&lt;p&gt;Remote Deployment to Glassfish v6 using Cargo Local Deployer was originally published in ITNEXT on Medium, where people are continuing the conversation by highlighting and responding to this story.&lt;/p&gt;" />
<meta property="og:description" content="This is an addition to the existing deploying Jakarta EE 9 applications to Glassfish v6 using Cargo maven plugin. Cargo maven plugin 1.8.3 will include a glasfish6x containerId for the new Glassfish v6. In 1.8.2 or previous versions, it allows you use a JSR88 specification(Deployment) based remote deployer with a runtime configuration to deploy applications to a running Glassfish server. This will stop to work when switching to use a glassfish6x container due to the changes happen in Jakarta EE 9 and Glassfish v6. The JSR88 is removed in the further Jakarta EE 9, check the 6.1.4. Removed Jakarta Technologies section of Jakarta EE 9 specification. And the deployment-client artifact which is existed for Glassfish v5 release train is not available in Glassfish v6. Correspondingly cargo glassfish6x container will not include a remote deployer, and you can not configure a runtime configuration as before. But you can use the local deployer to deploy the applications to remote servers. &lt;profile&gt; &lt;id&gt;glassfish-local-deployer&lt;/id&gt; &lt;properties&gt; &lt;cargo.hostname&gt;localhost&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;8080&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;4848&lt;/cargo.glassfish.admin.port&gt; &lt;cargo.zipUrlInstaller.downloadDir&gt;${project.build.directory}/../installs &lt;/cargo.zipUrlInstaller.downloadDir&gt; &lt;/properties&gt; &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.codehaus.cargo&lt;/groupId&gt; &lt;artifactId&gt;cargo-maven2-plugin&lt;/artifactId&gt; &lt;configuration&gt; &lt;container&gt; &lt;containerId&gt;glassfish6x&lt;/containerId&gt; &lt;zipUrlInstaller&gt; &lt;url&gt; https://download.eclipse.org/ee4j/glassfish/glassfish-${glassfish.version}.zip &lt;/url&gt; &lt;downloadDir&gt;${cargo.zipUrlInstaller.downloadDir}&lt;/downloadDir&gt; &lt;/zipUrlInstaller&gt; &lt;!-- or use artifactInstaller--&gt; &lt;!--&lt;artifactInstaller&gt; &lt;groupId&gt;org.glassfish.main.distributions&lt;/groupId&gt; &lt;artifactId&gt;glassfish&lt;/artifactId&gt; &lt;version&gt;${glassfish.version}&lt;/version&gt; &lt;/artifactInstaller&gt;--&gt; &lt;/container&gt; &lt;configuration&gt; &lt;!-- the configuration use to deploy --&gt; &lt;home&gt;${project.build.directory}/glassfish6x-home&lt;/home&gt; &lt;properties&gt; &lt;cargo.hostname&gt;${cargo.hostname}&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;${cargo.servlet.port}&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;${cargo.glassfish.admin.port} &lt;/cargo.glassfish.admin.port&gt; &lt;cargo.remote.username&gt;admin&lt;/cargo.remote.username&gt; &lt;cargo.remote.password&gt;&lt;/cargo.remote.password&gt; &lt;/properties&gt; &lt;/configuration&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/build&gt;&lt;/profile&gt; The above configuration also work in the existing glassfish5x containerId. The side effect is you have to download a copy of Glassfish dist, the local deployer uses the Glassfish built-in asadmin tooling command to perform the deployment. NOTE: The cargo.hostname is the hostname/address of the target Glassfish server to deploy. Execute the following command to package and deploy the application to the target server. mvn clean package cargo:deploy -Pglassfish-local-deployer To undeploy the application, execute the following command. mvn cargo:undeploy -Pglassfish-local-deployer Check the Cargo official guide for the instructions of Remote Deployment to Glassfish v6 and the changes of Cargo glassfish6x containerid. &lt;hr&gt;&lt;p&gt;Remote Deployment to Glassfish v6 using Cargo Local Deployer was originally published in ITNEXT on Medium, where people are continuing the conversation by highlighting and responding to this story.&lt;/p&gt;" />
<meta property="og:site_name" content="blank" />
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2020-12-04T00:00:00+00:00" />
<meta name="twitter:card" content="summary" />
<meta property="twitter:title" content="Remote Deployment to Glassfish v6 using Cargo Local Deployer" />
<script type="application/ld+json">
{"datePublished":"2020-12-04T00:00:00+00:00","description":"This is an addition to the existing deploying Jakarta EE 9 applications to Glassfish v6 using Cargo maven plugin. Cargo maven plugin 1.8.3 will include a glasfish6x containerId for the new Glassfish v6. In 1.8.2 or previous versions, it allows you use a JSR88 specification(Deployment) based remote deployer with a runtime configuration to deploy applications to a running Glassfish server. This will stop to work when switching to use a glassfish6x container due to the changes happen in Jakarta EE 9 and Glassfish v6. The JSR88 is removed in the further Jakarta EE 9, check the 6.1.4. Removed Jakarta Technologies section of Jakarta EE 9 specification. And the deployment-client artifact which is existed for Glassfish v5 release train is not available in Glassfish v6. Correspondingly cargo glassfish6x container will not include a remote deployer, and you can not configure a runtime configuration as before. But you can use the local deployer to deploy the applications to remote servers. &lt;profile&gt; &lt;id&gt;glassfish-local-deployer&lt;/id&gt; &lt;properties&gt; &lt;cargo.hostname&gt;localhost&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;8080&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;4848&lt;/cargo.glassfish.admin.port&gt; &lt;cargo.zipUrlInstaller.downloadDir&gt;${project.build.directory}/../installs &lt;/cargo.zipUrlInstaller.downloadDir&gt; &lt;/properties&gt; &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.codehaus.cargo&lt;/groupId&gt; &lt;artifactId&gt;cargo-maven2-plugin&lt;/artifactId&gt; &lt;configuration&gt; &lt;container&gt; &lt;containerId&gt;glassfish6x&lt;/containerId&gt; &lt;zipUrlInstaller&gt; &lt;url&gt; https://download.eclipse.org/ee4j/glassfish/glassfish-${glassfish.version}.zip &lt;/url&gt; &lt;downloadDir&gt;${cargo.zipUrlInstaller.downloadDir}&lt;/downloadDir&gt; &lt;/zipUrlInstaller&gt; &lt;!-- or use artifactInstaller--&gt; &lt;!--&lt;artifactInstaller&gt; &lt;groupId&gt;org.glassfish.main.distributions&lt;/groupId&gt; &lt;artifactId&gt;glassfish&lt;/artifactId&gt; &lt;version&gt;${glassfish.version}&lt;/version&gt; &lt;/artifactInstaller&gt;--&gt; &lt;/container&gt; &lt;configuration&gt; &lt;!-- the configuration use to deploy --&gt; &lt;home&gt;${project.build.directory}/glassfish6x-home&lt;/home&gt; &lt;properties&gt; &lt;cargo.hostname&gt;${cargo.hostname}&lt;/cargo.hostname&gt; &lt;cargo.servlet.port&gt;${cargo.servlet.port}&lt;/cargo.servlet.port&gt; &lt;cargo.glassfish.admin.port&gt;${cargo.glassfish.admin.port} &lt;/cargo.glassfish.admin.port&gt; &lt;cargo.remote.username&gt;admin&lt;/cargo.remote.username&gt; &lt;cargo.remote.password&gt;&lt;/cargo.remote.password&gt; &lt;/properties&gt; &lt;/configuration&gt; &lt;/configuration&gt; &lt;/plugin&gt; &lt;/plugins&gt; &lt;/build&gt;&lt;/profile&gt; The above configuration also work in the existing glassfish5x containerId. The side effect is you have to download a copy of Glassfish dist, the local deployer uses the Glassfish built-in asadmin tooling command to perform the deployment. NOTE: The cargo.hostname is the hostname/address of the target Glassfish server to deploy. Execute the following command to package and deploy the application to the target server. mvn clean package cargo:deploy -Pglassfish-local-deployer To undeploy the application, execute the following command. mvn cargo:undeploy -Pglassfish-local-deployer Check the Cargo official guide for the instructions of Remote Deployment to Glassfish v6 and the changes of Cargo glassfish6x containerid. &lt;hr&gt;&lt;p&gt;Remote Deployment to Glassfish v6 using Cargo Local Deployer was originally published in ITNEXT on Medium, where people are continuing the conversation by highlighting and responding to this story.&lt;/p&gt;","mainEntityOfPage":{"@type":"WebPage","@id":"/blog/2020/remote-deployment-to-glassfish-v6-using-cargo-local-deployer/"},"url":"/blog/2020/remote-deployment-to-glassfish-v6-using-cargo-local-deployer/","@type":"BlogPosting","headline":"Remote Deployment to Glassfish v6 using Cargo Local Deployer","dateModified":"2020-12-04T00:00:00+00:00","@context":"https://schema.org"}</script>
<!-- End Jekyll SEO tag -->

</head>

<body
  class="fixed-top-nav ">

  <!-- Header -->

  <header>

    <!-- Nav Bar -->
    <nav id="navbar" class="navbar navbar-light navbar-expand-sm fixed-top">
    <div class="container">
      
      <a class="navbar-brand title font-weight-lighter" href="/">
       <span class="font-weight-bold">Hantsy</span>   Bai
      </a>
      
      <!-- Navbar Toggle -->
      <button class="navbar-toggler collapsed ml-auto" type="button" data-toggle="collapse" data-target="#navbarNav" aria-controls="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
        <span class="sr-only">Toggle navigation</span>
        <span class="icon-bar top-bar"></span>
        <span class="icon-bar middle-bar"></span>
        <span class="icon-bar bottom-bar"></span>
      </button>
      <div class="collapse navbar-collapse text-right" id="navbarNav">
        <ul class="navbar-nav ml-auto flex-nowrap">
          <!-- About -->
          <li class="nav-item ">
            <a class="nav-link" href="/">
              about
              
            </a>
          </li>
          
          <!-- Blog -->
          <li class="nav-item active">
            <a class="nav-link" href="/blog/">
              blog
              
            </a>
          </li>
          
          <!-- Other pages -->
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          
          <li class="nav-item ">
              <a class="nav-link" href="/projects/">
                projects
                
              </a>
          </li>
          
          
          
          <li class="nav-item ">
              <a class="nav-link" href="/publications/">
                publications
                
              </a>
          </li>
          
          
          
          <li class="nav-item ">
              <a class="nav-link" href="/service/">
                service
                
              </a>
          </li>
          
          
          
            <div class = "toggle-container">
              <a id = "light-toggle">
                  <i class="fas fa-moon"></i>
                  <i class="fas fa-sun"></i>
              </a>
            </div>
          
        </ul>
      </div>
    </div>
  </nav>

</header>


  <!-- Content -->

  <div class="container mt-5">
    

<div class="post">

  <header class="post-header">
    <h1 class="post-title">Remote Deployment to Glassfish v6 using Cargo Local Deployer</h1>
    <p class="post-meta">December 4, 2020</p>
  </header>

  <article class="post-content">
    <figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZgar-TMaqJ9r-ovXsLz_A.png" /></figure><blockquote><em>This is an addition to the existing </em><a href="https://github.com/hantsy/jakartaee9-starter-boilerplate/blob/master/docs/docs/deploy-cargo.md"><em>deploying Jakarta EE 9 applications to Glassfish v6 using Cargo maven plugin</em></a><em>.</em></blockquote><p><a href="https://codehaus-cargo.github.io">Cargo maven plugin</a> 1.8.3 will include a glasfish6x <em>containerId</em> for the new Glassfish v6. In 1.8.2 or previous versions, it allows you use a JSR88 specification(Deployment) based remote deployer with a <em>runtime</em> configuration to deploy applications to a running Glassfish server.</p><p>This will stop to work when switching to use a glassfish6x container due to the changes happen in Jakarta EE 9 and Glassfish v6.</p><p>The JSR88 is removed in the further Jakarta EE 9, check the <a href="https://jakarta.ee/specifications/platform/9/jakarta-platform-spec-9.html#a2333">6.1.4. Removed Jakarta Technologies</a> section of Jakarta EE 9 specification. And the deployment-client artifact which is existed for Glassfish v5 release train is not available in Glassfish v6.</p><p>Correspondingly cargo glassfish6x container will not include a remote deployer, and you can not configure a <em>runtime</em> configuration as before. But you can use the local deployer to deploy the applications to remote servers.</p><pre>&lt;profile&gt;<br>    &lt;id&gt;glassfish-local-deployer&lt;/id&gt;<br>    &lt;properties&gt;<br>        &lt;cargo.hostname&gt;localhost&lt;/cargo.hostname&gt;<br>        &lt;cargo.servlet.port&gt;8080&lt;/cargo.servlet.port&gt;<br>        &lt;cargo.glassfish.admin.port&gt;4848&lt;/cargo.glassfish.admin.port&gt;<br>        &lt;cargo.zipUrlInstaller.downloadDir&gt;${project.build.directory}/../installs<br>        &lt;/cargo.zipUrlInstaller.downloadDir&gt;<br>    &lt;/properties&gt;</pre><pre>    &lt;build&gt;<br>        &lt;plugins&gt;<br>            &lt;plugin&gt;<br>                &lt;groupId&gt;org.codehaus.cargo&lt;/groupId&gt;<br>                &lt;artifactId&gt;cargo-maven2-plugin&lt;/artifactId&gt;<br>                &lt;configuration&gt;<br>                    &lt;container&gt;<br>                        &lt;containerId&gt;glassfish6x&lt;/containerId&gt;<br>                        &lt;zipUrlInstaller&gt;<br>                            &lt;url&gt;<br>                               <a href="https://download.eclipse.org/ee4j/glassfish/glassfish-${glassfish.version}.zip">https://download.eclipse.org/ee4j/glassfish/glassfish-${glassfish.version}.zip</a><br>                            &lt;/url&gt;<br>                            &lt;downloadDir&gt;${cargo.zipUrlInstaller.downloadDir}&lt;/downloadDir&gt;<br>                        &lt;/zipUrlInstaller&gt;<br>                        &lt;!-- or use artifactInstaller--&gt;<br>                        &lt;!--&lt;artifactInstaller&gt;<br>                                    &lt;groupId&gt;org.glassfish.main.distributions&lt;/groupId&gt;<br>                                    &lt;artifactId&gt;glassfish&lt;/artifactId&gt;<br>                                    &lt;version&gt;${glassfish.version}&lt;/version&gt;<br>                                &lt;/artifactInstaller&gt;--&gt;<br>                    &lt;/container&gt;<br>                    &lt;configuration&gt;<br>                        &lt;!-- the configuration use to deploy --&gt;<br>                        &lt;home&gt;${project.build.directory}/glassfish6x-home&lt;/home&gt;<br>                        &lt;properties&gt;<br>                            &lt;cargo.hostname&gt;${cargo.hostname}&lt;/cargo.hostname&gt;<br>                            &lt;cargo.servlet.port&gt;${cargo.servlet.port}&lt;/cargo.servlet.port&gt;<br>                            &lt;cargo.glassfish.admin.port&gt;${cargo.glassfish.admin.port}<br>                            &lt;/cargo.glassfish.admin.port&gt;<br>                            &lt;cargo.remote.username&gt;admin&lt;/cargo.remote.username&gt;<br>                            &lt;cargo.remote.password&gt;&lt;/cargo.remote.password&gt;<br>                        &lt;/properties&gt;<br>                    &lt;/configuration&gt;<br>                &lt;/configuration&gt;<br>            &lt;/plugin&gt;<br>        &lt;/plugins&gt;<br>    &lt;/build&gt;<br>&lt;/profile&gt;</pre><blockquote><em>The above configuration also work in the existing </em><em>glassfish5x containerId.</em></blockquote><p>The side effect is you have to download a copy of Glassfish dist, the local deployer uses the Glassfish built-in asadmin tooling command to perform the deployment.</p><blockquote><em>NOTE: The </em><em>cargo.hostname is the hostname/address of the target Glassfish server to deploy.</em></blockquote><p>Execute the following command to package and deploy the application to the target server.</p><pre>mvn clean package cargo:deploy -Pglassfish-local-deployer</pre><p>To undeploy the application, execute the following command.</p><pre>mvn  cargo:undeploy -Pglassfish-local-deployer</pre><p>Check the Cargo official guide for <a href="https://codehaus-cargo.github.io/cargo/Remote+deployments+to+GlassFish+6.x.html">the instructions of Remote Deployment to Glassfish v6</a> and <a href="https://codehaus-cargo.github.io/cargo/GlassFish+6.x.html">the changes of Cargo glassfish6x containerid</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65983c12aba7" width="1" height="1" alt=""><hr><p><a href="https://itnext.io/remote-deployment-to-glassfish-v6-using-cargo-local-deployer-65983c12aba7">Remote Deployment to Glassfish v6 using Cargo Local Deployer</a> was originally published in <a href="https://itnext.io">ITNEXT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>

  </article>

  

</div>

  </div>

  <!-- Footer -->

  
<footer class="fixed-bottom">
  <div class="container mt-0">
    &copy; Copyright 2021 Hantsy  Bai.
    <span class="mr-auto"></span>
    Powered by <a href="http://jekyllrb.com/" target="_blank">Jekyll</a> with <a href="https://github.com/alshedivat/al-folio">al-folio</a> theme.

    
    

  </div>
</footer>



</body>

<!-- Bootsrap & MDB scripts -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/2.4.4/umd/popper.min.js" integrity="sha512-eUQ9hGdLjBjY3F41CScH3UX+4JDSI9zXeroz7hJ+RteoCaY+GP/LDoM8AO+Pt+DRFw3nXqsjh9Zsts8hnYv8/A==" crossorigin="anonymous"></script>
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.5.2/js/bootstrap.min.js" integrity="sha512-M5KW3ztuIICmVIhjSqXe01oV2bpe248gOxqmlcYrEzAvws7Pw3z6BK0iGbrwvdrUQUhi3eXgtxp5I8PDo9YfjQ==" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/mdbootstrap/4.19.1/js/mdb.min.js" integrity="sha512-Mug9KHKmroQFMLm93zGrjhibM2z2Obg9l6qFG2qKjXEXkMp/VDkI4uju9m4QKPjWSwQ6O2qzZEnJDEeCw0Blcw==" crossorigin="anonymous"></script>


<!-- Mansory & imagesLoaded -->
<script defer src="https://unpkg.com/masonry-layout@4/dist/masonry.pkgd.min.js"></script>
<script defer src="https://unpkg.com/imagesloaded@4/imagesloaded.pkgd.min.js"></script>
<script defer src="/assets/js/mansory.js" type="text/javascript"></script>





<!-- Load Common JS -->
<script src="/assets/js/common.js"></script>


</html>
